So, I'm trying to restore a gitolite installation (along with all repositories) from TimeMachine onto my new iMac (Mac OSX 10.13.4). It's been failing, so I thought I'd try testing gitolite.
I ran the Trying out gitolite safely on my machine, that that fails too. Below are the test results, that I don't know what to make of and where to look. Any help is appreciated:
Test Summary Report
-------------------
t/basic.t (Wstat: 0 Tests: 217 Failed: 1)
Failed test: 1
t/info-json.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/reference.t (Wstat: 0 Tests: 16 Failed: 7)
Failed tests: 10-16
t/ssh-authkeys.t (Wstat: 0 Tests: 49 Failed: 2)
Failed tests: 38, 42
t/ssh-basic.t (Wstat: 0 Tests: 26 Failed: 10)
Failed tests: 15-23, 25
t/vrefs-1.t (Wstat: 0 Tests: 88 Failed: 23)
Failed tests: 43-47, 49, 56-60, 62, 69-73, 79-82, 87-88
t/vrefs-2.t (Wstat: 0 Tests: 72 Failed: 8)
Failed tests: 56-60, 64, 66, 68
t/writable.t (Wstat: 0 Tests: 66 Failed: 5)
Failed tests: 60, 62-63, 65-66
Instead, you could make a fresh install, and then restore your bare repos that were in the folder repositories/, including the gitolite-admin.git/ one (which includes all the configurations)
See "bringing existing repos into gitoliteď": run, after restoring those repos in your new gitolite instance, gitolite setup.
Related
We have the following output at the end of our Jest test base:
Test Suites: 273 passed, 273 total
Tests: 1 skipped, 1923 passed, 1924 total
Snapshots: 61 passed, 61 total
Time: 38.885 s, estimated 39 s
You see there is one skipped test.
When I search my test files either for it.skip or test.skip or generally skip I find nothing.
What I also tried is outputting the test run into JSON via:
jest --json --outputFile=testrun.json
In the top of the file I find this information:
{
"numFailedTestSuites": 0,
"numFailedTests": 0,
"numPassedTestSuites": 273,
"numPassedTests": 1923,
"numPendingTestSuites": 0,
"numPendingTests": 1,
"numRuntimeErrorTestSuites": 0,
"numTodoTests": 0,
"numTotalTestSuites": 273,
"numTotalTests": 1924,
...
}
so it looks like that numPendingTests is the one pointing to the skipped one. But when I search the output file, again, no trace of a skipped test. In fact, I did a search for "status": "[a-z]and there is no other status to be found than passed.
Short of looking through 270+ test suites, how else could a skipped test hide from me? Is there any way to find it?
As mentioned by johnrsharp as a comment, another way to skip tests in Jest is to prefix the term it(test) with x- so if you want to scan the files for skipped tests, you also need to look out for xit or xtest.
I am learning SystemTap and I have created a simple C program to grasp the basics.
When I run the program and a probe in the hosting system, the probe works flawlessly, but when I copy the exact same process in a container I run into some problems (container is running in privileged mode).
When I leave both the program and probe running for a few seconds a WARNING message appears and this is what the stap output looks like after I stop the program:
[root#client ~]# stap -v tmp-probe.stp /root/tmp
Pass 1: parsed user script and 482 library scripts using 115544virt/94804res/16320shr/78424data kb, in 140usr/20sys/168real ms.
Pass 2: analyzed script: 2 probes, 1 function, 0 embeds, 1 global using 116996virt/97852res/17612shr/79876data kb, in 10usr/0sys/6real ms.
Pass 3: using cached /root/.systemtap/cache/73/stap_7357b5a96975af17d2210a04bada9b6a_1260.c
Pass 4: using cached /root/.systemtap/cache/73/stap_7357b5a96975af17d2210a04bada9b6a_1260.ko
Pass 5: starting run.
WARNING: probe process("/root/tmp").statement(0x40113a) at inode-offset 12761464:0000000060a7c1a2 registration error [man warning::pass5] (rc -5)
0
Pass 5: run completed in 0usr/70sys/3579real ms.
The binary has been compiled with: gcc -ggdb3 -O0 tmp.c -o tmp and contains these probe points:
process("/root/tmp").begin $syscall:long $arg1:long $arg2:long $arg3:long $arg4:long $arg5:long $arg6:long
process("/root/tmp").end $syscall:long $arg1:long $arg2:long $arg3:long $arg4:long $arg5:long $arg6:long
process("/root/tmp").plt("puts")
process("/root/tmp").plt("sleep")
process("/root/tmp").syscall $syscall:long $arg1:long $arg2:long $arg3:long $arg4:long $arg5:long $arg6:long
process("/root/tmp").mark("in_test")
process("/root/tmp").function("main#/root/tmp.c:11")
process("/root/tmp").function("test#/root/tmp.c:5")
tmp.c:
#include <stdio.h>
#include <sys/sdt.h>
#include <unistd.h>
void test() {
STAP_PROBE(test, in_test);
printf("here\n");
sleep(1);
}
int main() {
while (1) {
test();
}
}
tmp-probe.stp:
global cnt
probe process(#1).mark("in_test") {
cnt++
}
probe process(#1).end {
printf("%ld\n", cnt)
exit()
}
A more verbose stap output:
[root#client ~]# stap -vv tmp-probe.stp /root/tmp
Systemtap translator/driver (version 4.6/0.186, rpm 4.6-4.fc35)
Copyright (C) 2005-2021 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 5.15.0-rc7
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON3 LIBRPM LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE MONITOR_LIBS
Created temporary directory "/tmp/stapRsSKyO"
Session arch: x86_64 release: 5.16.20-200.fc35.x86_64
Build tree: "/lib/modules/5.16.20-200.fc35.x86_64/build"
Searched for library macro files: "/usr/share/systemtap/tapset/linux", found: 7, processed: 7
Searched for library macro files: "/usr/share/systemtap/tapset", found: 11, processed: 11
Searched: "/usr/share/systemtap/tapset/linux/x86_64", found: 20, processed: 20
Searched: "/usr/share/systemtap/tapset/linux", found: 407, processed: 407
Searched: "/usr/share/systemtap/tapset/x86_64", found: 1, processed: 1
Searched: "/usr/share/systemtap/tapset", found: 36, processed: 36
Pass 1: parsed user script and 482 library scripts using 115580virt/95008res/16520shr/78460data kb, in 130usr/30sys/163real ms.
derive-probes (location #0): process("/root/tmp").mark("in_test") of keyword at tmp-probe.stp:3:1
derive-probes (location #0): process("/root/tmp").end of keyword at tmp-probe.stp:7:1
Pass 2: analyzed script: 2 probes, 1 function, 0 embeds, 1 global using 117032virt/97860res/17624shr/79912data kb, in 10usr/0sys/6real ms.
Pass 3: using cached /root/.systemtap/cache/73/stap_7357b5a96975af17d2210a04bada9b6a_1260.c
Pass 4: using cached /root/.systemtap/cache/73/stap_7357b5a96975af17d2210a04bada9b6a_1260.ko
Pass 5: starting run.
Running /usr/bin/staprun -v -R /tmp/stapRsSKyO/stap_7357b5a96975af17d2210a04bada9b6a_1260.ko
staprun:insert_module:191 Module stap_7357b5a96975af17d2210a04bada9b_698092 inserted from file /tmp/stapRsSKyO/stap_7357b5a96975af17d2210a04bada9b6a_1260.ko
WARNING: probe process("/root/tmp").statement(0x40113a) at inode-offset 12761464:0000000060a7c1a2 registration error [man warning::pass5] (rc -5)
0
stapio:cleanup_and_exit:352 detach=0
stapio:cleanup_and_exit:369 closing control channel
staprun:remove_module:292 Module stap_7357b5a96975af17d2210a04bada9b_698092 removed.
Spawn waitpid result (0x0): 0
Pass 5: run completed in 10usr/70sys/2428real ms.
Running rm -rf /tmp/stapRsSKyO
Spawn waitpid result (0x0): 0
Removed temporary directory "/tmp/stapRsSKyO"
I'm trying to run jmeter load testing scripts in non GUI mode to generate HTML report with below command
./jmeter.sh -n -t "/home/dsbloadtest/DSB_New_21_01_2022/apache-jmeter-5.4.3/dsb_test_plans/SERVICE_BOOKING.jmx" -l /home/dsbloadtest/DSB_New_21_01_2022/apache-jmeter-5.4.3/dsb_test_results/testresults.csv -e -o /home/dsbloadtest/DSB_New_21_01_2022/apache-jmeter-5.4.3/dsb_test_results/HTMLReports
It was working fine, but now not getting the result as im getting as below
summary = 0 in 00:00:00 = \*\*\*\*\*\*/s Avg: 0 Min: 9223372036854775807 Max: -9223372036854775808 Err: 0 (0.00%)
Tidying up ... # Fri Apr 01 11:22:40 IST 2022 (1648792360414)
Error generating the report: org.apache.jmeter.report.core.SampleException: Could not read metadata !
... end of run
I have tried to generate HTML report in J meter non GUI mode.
summary = 0 in 00:00:00 = ******/s Avg: 0 Min: 9223372036854775807 Max: -9223372036854775808 Err: 0 (0.00%)
it means that JMeter didn't execute any Sampler, your testresults.csv is empty and you don't have any data to generate the dashboard from.
The reason for test failure normally can be figured out from jmeter.log file, the most common mistakes are:
the file referenced in the CSV Data Set Config doesn't exist
the JMeter Plugins used in the test are not installed for this particular JMeter instance
I am getting an error with the doppl SOAndroid app. I have successfully been through the PartyClickerSample.
iosApp[40373:656090] *** Terminating app due to uncaught exception 'JavaLangIllegalArgumentException', reason: 'java.lang.IllegalArgumentException: interface co.doppl.so.api.SOInterface is not visible from class loader'
*** First throw call stack:
(
0 CoreFoundation 0x000000010ef0c12b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x000000010b51ff41 objc_exception_throw + 48
2 doppllib 0x0000000108b2d0a6 JavaLangReflectProxy_getProxyClass0WithJavaLangClassLoader_withIOSClassArray_ + 1791
3 doppllib 0x0000000108b2d233 JavaLangReflectProxy_newProxyInstanceWithJavaLangClassLoader_withIOSClassArray_withJavaLangReflectInvocationHandler_ + 45
4 doppllib 0x0000000108aab120 -[Retrofit2Retrofit createWithIOSClass:] + 240
5 doppllib 0x0000000108ac39c5 SOARepository_init + 389
6 doppllib 0x0000000108ac4134 new_SOARepository_init + 52
7 doppllib 0x0000000108ac3bb0 +[SOARepository initialize] + 64
Why is the SOInterface not visible when it is in the config?
...
include 'co/doppl/so/api/**'
...
translatedPathPrefix 'co.doppl.so.api', 'SOAPI'
Also with the iosTest, the tests pass but get some BoringSsl statement:
********** Result for co.doppl.so.RepositoryTest **********
Success
Total: 1
Failures: 0
2018-02-23 09:50:58.086219-0600 iosTest[41775:778685] [BoringSSL] Function boringssl_session_errorlog: line 2871 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert
I keept searching and found the answer:
https://github.com/doppllib/SOAndroid/issues/1
"Need to add 'prefixes.properties' to the main app bundle".
Same as was done with the testIOS app.
I am trying to run the demo for UITest on iOS platform here.
I can not run the UI test, even though building the project without a problem.
This is the error information:
SetUp : Calabash.XDB.Core.Exceptions.DeviceAgentException : Failed to launch simulator
ExitCode: 134
2016-11-23 12:00:01.767 iOSDeviceManager[36474:1504101] CoreSimulator: Loading from /Applications/Xcode 8.2-beta.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework
2016-11-23 12:00:01.772 iOSDeviceManager[36474:1504101] CoreSimulator: Successfully loaded
2016-11-23 12:00:01.773 iOSDeviceManager[36474:1504101] CoreSimulator: SimDevice has correct path of /Applications/Xcode 8.2-beta.app
2016-11-23 12:00:01.773 iOSDeviceManager[36474:1504101] SimulatorKit: Loading from /Applications/Xcode 8.2-beta.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework
2016-11-23 12:00:01.795 iOSDeviceManager[36474:1504101] SimulatorKit: Successfully loaded
2016-11-23 12:00:01.795 iOSDeviceManager[36474:1504101] SimulatorKit: SimDeviceFramebufferService has correct path of /Applications/Xcode 8.2-beta.app
2016-11-23 12:00:01.796 iOSDeviceManager[36474:1504101] Loaded All Private Frameworks [CoreSimulator, SimulatorKit]
2016-11-23 12:00:01.883 iOSDeviceManager[36474:1504101] Completed Pool Preconditons
2016-11-23 12:00:01.939 iOSDeviceManager[36474:1504101] *** Assertion failure in -[FBSimulatorConfiguration initWithNamedDevice:os:auxillaryDirectory:], /Users/chrisf/FBSimulatorControl/FBSimulatorControl/Configuration/FBSimulatorConfiguration.m:32
2016-11-23 12:00:02.056 iOSDeviceManager[36474:1504101] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: os'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff832256fb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff97a2ca2a objc_exception_throw + 48
2 CoreFoundation 0x00007fff8322a252 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fff84c7d390 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 FBSimulatorControl 0x000000010d2cef3f -[FBSimulatorConfiguration initWithNamedDevice:os:auxillaryDirectory:] + 444
5 FBSimulatorControl 0x000000010d2cf0a3 __48+[FBSimulatorConfiguration defaultConfiguration]_block_invoke + 108
6 libdispatch.dylib 0x00007fff982d3128 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff982d30e5 dispatch_once_f + 38
8 FBSimulatorControl 0x000000010d2cf034 +[FBSimulatorConfiguration defaultConfiguration] + 45
9 FBSimulatorControl 0x000000010d2fc253 +[FBSimulatorConfiguration(CoreSimulator) inferSimulatorConfigurationFromDevice:error:] + 347
10 FBSimulatorControl 0x000000010d2f657f +[FBSimulator fromSimDevice:configuration:launchdSimProcess:containerApplicationProcess:set:] + 178
11 FBSimulatorControl 0x000000010d2f8157 -[FBSimulatorInflationStrategy inflateSimulators:availableDevices:previouslyIdentifiedContainerApplications:] + 810
12 FBSimulatorControl 0x000000010d2f7db8 -[FBSimulatorInflationStrategy inflateFromDevices:exitingSimulators:] + 891
13 FBSimulatorControl 0x000000010d2d615d -[FBSimulatorSet allSimulators] + 129
14 FBSimulatorControl 0x000000010d2d45d5 -[FBSimulatorSet query:] + 108
15 iOSDeviceManager 0x000000010d1609c1 +[Simulator simulatorWithDeviceID:] + 238
16 iOSDeviceManager 0x000000010d1614f5 +[Simulator launchSimulator:] + 88
17 iOSDeviceManager 0x000000010d161ec7 +[LaunchSimulatorCommand execute:] + 74
18 iOSDeviceManager 0x000000010d15cd4a +[CLI process:] + 1171
19 iOSDeviceManager 0x000000010d121504 main + 104
20 libdyld.dylib 0x00007fff98309255 start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
I am using Xamarin test cloud to run UITest of Xamarin android and xamarin ios project. I have tried both. For Xamarin.ios project, my setup method looks like below,
app = ConfigureApp
.iOS
.PreferIdeSettings()
.StartApp();
As instructed in default UITest, you need to perform below steps.
Edit the AppDelegate class and add the following snippet to the FinishedLaunching method...
#if ENABLE_TEST_CLOUD
Xamarin.Calabash.Start();
#endif
Make sure you are adding "ENABLE_TEST_CLOUD" debug variable in debug configuration of project or remove if, endif (always allow Xamarin.calabash.start().
and post the UiTest to xamarin test cloud from release configuration build.
Just make sure in this case, remove above statement when you are submiiting your app to app store.
In unit test window (of Xamarin studio), add ios app and then run the test with test cloud. Make sure you have xamarin account to run test on test cloud.
Then it asks devices on which test will be running. You can select 1 or many.