Fixes #16
Fixes #16
Conversation
|
Ah, I see now. Tests run fine locally for me. I have really limited experience with CircleCI, and confused why the tests aren't triggering consistently on pull requests. I've never seen this with TravisCI. Any idea what's going on here? Something configured wrong maybe? |
|
No idea, web hooks getting lost in some queue on either Github or CircleCI side I guess. It finished successfully though https://circleci.com/gh/kba/bagit-profiles-validator/tree/fixes This does happen with Travis as well, though not as often. With Travis, it often happens that builds fail because network glitches on their part prevent a container booting. Main reason why I prefer CircleCI is that it is much faster and uses newer containers (Travis is still running ubuntu 14.04). |
|
The default for this is "off". |
That's to prevent people stealing any environment secrets (eg AWS keys) by sending a PR with malicious code. I can't wrap my head around it right now why not this was built at all if PR building was off. Or why in #17 only 2 of 5 tests sent success status. If nothing else works, "Restart workflow" (Circle) or "Rebuild" (Travis) usually does. |
|
Yeah, it's definitely behaving strangely. I don't see this or the other two PRs here. Am I missing something? |
One error was because https://github.com/bagit-profiles/bagit-profiles/blob/master/bagProfileBar.json changed.
The other error was because absolute paths were checked against relative wildcards. No idea how that slipped through.