Hey ATC, Can we change the CI jobs ( https://builds.apache.org/search/?q=trafficcontrol) to run weasel after the other containers exit?
When running against https://github.com/apache/trafficcontrol/pull/4758 , weasel fails because it references files that existed when it started but had since been deleted. Example (search for panic: Failed when enumerating working directory): https://builds.apache.org/job/trafficcontrol-PR/6173/consoleText After speaking to the author of comcast/weasel (alficles), it sounds like the problem exists in golang's filesystem walker itself, so a fix would involve rewriting that library and would be easier to just avoid. To avoid the issue, the non-weasel containers would run before weasel to avoid the filesystem changing while weasel runs. Is this doable? The PR job seems to consistently fail for https://builds.apache.org/job/trafficcontrol-PR/6173/consoleText ,so it should not be merged until the CI jobs are changed to accommodate weasel. -Zach
