New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
elasticmq-server: 0.14.6 -> 1.2.0, add passthru.tests #97299
elasticmq-server: 0.14.6 -> 1.2.0, add passthru.tests #97299
Conversation
@ofborg build elasticmq-server-bin elasticmq-server-bin.tests |
@risicle please resolve the merge conflict. |
799c330
to
49eb812
Compare
@ofborg build elasticmq-server-bin elasticmq-server-bin.tests |
49eb812
to
8cf31d0
Compare
Result of 1 package built:
|
I marked this as stale due to inactivity. → More info |
@risicle perhaps now we should update to https://github.com/softwaremill/elasticmq/releases/tag/v1.2.0 ? |
Totally forgot about this. Yes, perhaps. |
8cf31d0
to
5a94051
Compare
simply starts an elasticmq server with a queue "foobar", attempts to put a message to it from python then checks it arrives
5a94051
to
0fec93a
Compare
Rebased, bumped, tests pass on nixos x86_64 and macos 10.15 |
Motivation for this change
Added quite a simple test to check basic operation of the queue.
Still, it's the first
passthru.tests
I've written, and I don't know whether e.g. detaching a process here is considered "ok". It feels a little less wrong than doing it incheckPhase
.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)