75
70
22
A simple job queue built on AWS SQS and NodeJS using ES6/2015.
A gem to screencap webpages in ruby. Uses Phantom.js under the hood.
A fully pluggable tool for identifying and reporting on patterns in JavaScript.
A simple tool that verifies if files have been formatted using prettier-eslint.
Events
bazel test generate test.xml miss "classname" which cannot pass the junit schema check
I think there are cases where we can't always override the xml, like if the test_timeout has been exceeded? As far as I can tell, Bazel will still output it's own xml.
bazel test generate test.xml miss "classname" which cannot pass the junit schema check
(ii) I wouldn't be opposed to changing generate-xml.sh to insert a dummy classname attribute. But that wouldn't help the situation where a test runner produces a test.xml file that doesn't use the attribute.
@haxorz I think this is a good option. If there are test runners overriding the default xml file I would think the onus would be on the test runner to produce a valid result.
